fix(corpus): tolerate transient database startup - #50
Merged
Conversation
…try-20260804 # Conflicts: # crates/corpus-core/src/db.rs
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Corpus was crash-looping when its Cloud SQL proxy was present but the database endpoint was not yet accepting connections. Startup now retries the pool connection with a bounded backoff and a per-attempt timeout, allowing the server to reach migrations once the proxy becomes ready while still failing promptly on a persistent outage.
Validation
cargo fmt --checkcargo clippy -p corpus-core --all-targets -- -D warningscargo test -p corpus-core— 97 unit tests and all package integration/doc tests passedPost-deploy validation
After the Corpus image is promoted through the deploy repository, validate the
corpusArgo application andcorpus-serverrollout in production. Confirm the pod reaches Ready without repeated database connection failures and that the Cloud SQL proxy sidecar remains healthy.